-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Split codegen backend check step into two and don't run it with x check compiler
#145340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Split codegen backend check step into two and don't run it with x check compiler
#145340
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, yeah it always felt a bit strange when ./x check compiler
checks cg backends 👍
impl Step for GccCodegenBackend { | ||
type Output = (); | ||
|
||
const ONLY_HOSTS: bool = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remark: will conflict with #145324
☔ The latest upstream changes (presumably #145131) made this pull request unmergeable. Please resolve the merge conflicts. |
819462e
to
2a2903c
Compare
Rebased. @bors r=jieyouxu |
This reduces the amount of work that is done during
x check compiler
. We still check both backends duringx check
by defaut, even if they are not inrust.codegen-backends
, as just checking them shouldn't require expensive preparations, like building GCC.r? @jieyouxu